<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic id="topic1"><title id="da20941">DROP OPERATOR FAMILY</title><body><p id="sql_command_desc">Removes an operator family.</p><section id="section2"><title>Synopsis</title><codeblock id="sql_command_synopsis">DROP OPERATOR FAMILY [IF EXISTS] <varname>name</varname> USING <varname>index_method</varname> [CASCADE | RESTRICT]</codeblock></section><section id="section3"><title>Description</title><p><codeph>DROP OPERATOR FAMILY</codeph> drops an existing operator family. To run this command
        you must be the owner of the operator family.</p>
      <p><codeph>DROP OPERATOR FAMILY</codeph> includes dropping any operator classes contained in
        the family, but it does not drop any of the operators or functions referenced by the family.
        If there are any indexes depending on operator classes within the family, you will need to
        specify <codeph>CASCADE</codeph> for the drop to complete.</p></section><section id="section4"><title>Parameters</title><parml><plentry><pt>IF EXISTS</pt><pd>Do not throw an error if the operator family does not exist. A notice is issued in this case. </pd></plentry><plentry><pt><varname>name</varname></pt><pd>The name (optionally schema-qualified) of an existing operator family.</pd></plentry><plentry><pt><varname>index_method</varname></pt><pd>The name of the index access method the operator family is for.</pd></plentry><plentry><pt>CASCADE</pt><pd>Automatically drop objects that depend on the operator family. </pd></plentry><plentry><pt>RESTRICT</pt><pd>Refuse to drop the operator family if any objects depend on it. This is the default. </pd></plentry></parml></section><section id="section5"><title>Examples</title><p>Remove the B-tree operator family <codeph>float_ops</codeph>: </p><codeblock>DROP OPERATOR FAMILY float_ops USING btree;</codeblock><p>This command will not succeed if there are any existing indexes that use the operator family. Add
          <codeph>CASCADE</codeph> to drop such indexes along with the operator family.</p></section><section id="section6"><title>Compatibility</title><p>There is no <codeph>DROP OPERATOR FAMILY</codeph> statement in the SQL standard. </p></section><section id="section7"><title>See Also</title><p><codeph><xref href="ALTER_OPERATOR_FAMILY.xml#topic1" type="topic" format="dita"/></codeph>,
            <codeph><xref href="CREATE_OPERATOR_FAMILY.xml#topic1" type="topic" format="dita"
          /></codeph>, <codeph><xref href="ALTER_OPERATOR_CLASS.xml#topic1" type="topic"
            format="dita"/></codeph>, <codeph><xref href="CREATE_OPERATOR_CLASS.xml#topic1/bx20941"
            >CREATE OPERATOR CLASS</xref></codeph>, <codeph><xref
            href="./DROP_OPERATOR_CLASS.xml#topic1" type="topic" format="dita"/></codeph></p></section></body></topic>
